placement of data_center and region — Add to CatalogOrganizationAttributes alongside the other organization attributes

• Alternatives: Add as top-level fields on CatalogOrganization directly
• Why: The fields appear in the attributes section of the API response (JsonApiOrganizationOutAttributes), making CatalogOrganizationAttributes the semantically correct home. Users access them consistently via organization.attributes.data_center, matching the pattern for name, hostname, etc.

excluding read-only fields from write requests — Override to_api() in CatalogOrganizationAttributes to explicitly construct JsonApiOrganizationInAttributes with only writable fields

• Alternatives: Rely on None-filtering in _get_snake_dict() — unsafe when fields are non-None, Place fields only on CatalogOrganization to avoid the write-path concern
• Why: data_center and region are absent from JsonApiOrganizationInAttributes (the write model), so they must not appear in PUT/PATCH bodies. An explicit to_api() override is the safest mechanism, consistent with the as_api_model() kwargs pattern in the architecture guide.

no init.py export change — Leave CatalogOrganizationAttributes unexported

• Alternatives: Export CatalogOrganizationAttributes for type-hinting convenience
• Why: CatalogOrganizationAttributes was not previously exported. The new fields are reachable via organization.attributes.data_center without requiring a new public symbol.

• The API server ignores unknown additional properties in write request bodies — consistent with existing code where oauth_issuer_location and oauth_client_id in CatalogOrganizationAttributes are also absent from JsonApiOrganizationInAttributes.
• data_center and region are truly server-generated read-only fields that users should never set explicitly; the OpenAPI diff description ('for diagnostic purposes') supports this.
• safeget(ea, ['data_center']) correctly retrieves the value from a JsonApiOrganizationOutAttributes OpenApiModel via snake_case key lookup, matching how the generated client normalises attribute names.

• The existing VCR cassette organization.yaml already contains dataCenter and region as empty strings in the response body (verified), so test_get_organization should pass without re-recording.
• Unit tests that pass a plain dict to from_api() exercise a slightly different code path than production (which uses a JsonApiOrganizationOut object), but safeget handles both dict and OpenApiModel so the tests remain valid.

• entity_model — Added data_center and region to CatalogOrganizationAttributes; added to_api() override to exclude them from write requests; updated CatalogOrganization.from_api() to populate them.
  • packages/gooddata-sdk/src/gooddata_sdk/catalog/organization/entity_model/organization.py
• tests — Added four unit tests (no cassettes): field storage, to_api() exclusion (parametrized), from_api() population, and from_api() absent-field handling.
  • packages/gooddata-sdk/tests/catalog/test_catalog_organization.py